Workflow-based change management and documentation system and method

ABSTRACT

A system includes a first database configured to store one or more workflow templates associated with one or more workflows, where each workflow is used to implement at least one change in at least one control system of an industrial plant. The system also includes a second database configured to document each of the one or more workflows. In addition, the system includes at least one processor configured to communicate with at least one user equipment and to provide at least one user interface to the at least one user equipment. The at least one user interface is configured to provide the one or more workflow templates and to receive definitions of the one or more workflows. The at least one user interface is also configured to provide the one or more workflows for implementation of the at least one change in the at least one control system.

TECHNICAL FIELD

This disclosure relates generally to industrial process control andautomation. More specifically, this disclosure relates to aworkflow-based change management and documentation system and method,such as for a manufacturing or processing plant.

BACKGROUND

Industrial process control and automation systems in manufacturing orprocessing plants often include components such as distributed controlsystems (DCSs), programmable logic controllers (PLCs), safetycontrollers, field devices, network devices, power supplies, anddistribution devices. The configuration, orientation, location, andother details related to these components are typically documented bydifferent vendors at the start of a plant. Interconnections,inter-dependencies, and minimum cross-information between systems areoften not available because (i) the components are often prepared inisolation by different vendors and (ii) co-ordination is limited to theconstruction and commissioning phase of a plant.

Bringing in changes under a disciplined approval system, tracing thechanges, studying impacts of the changes, and scheduling the changes inorder to align production planning, automatic documentation, and bestpractices distribution for configuration can be very difficult. Eachorganization may follow its own standard process and practices forchange requests. Further, cross-functional collaboration like reviews,approvals, and clearances often cannot be easily enforced. Eachorganization may have its own review processes and checklists that needto be enforced before a change is approved.

In some instances, change management processes are followed manually,which usually involves a lot of paperwork and can be error prone. Thiscan also be an issue during audit and root cause analysis to trace why achange was done. Optimal management of spare components, use of uniformengineering practices, facilitating causal analysis of defects andoutages, and optimal maintenance can also be difficult.

SUMMARY

This disclosure provides a workflow-based change management anddocumentation system and method.

In a first embodiment, a system includes a first database configured tostore one or more workflow templates associated with one or moreworkflows, where each workflow is used to implement at least one changein at least one control system of an industrial plant. The system alsoincludes a second database configured to document each of the one ormore workflows. In addition, the system includes at least one processorconfigured to communicate with at least one user equipment and toprovide at least one user interface to the at least one user equipment.The at least one user interface is configured to provide the one or moreworkflow templates and to receive definitions of the one or moreworkflows. The at least one user interface is also configured to providethe one or more workflows for implementation of the at least one changein the at least one control system.

In a second embodiment, a method for implementing a change in an controlsystem of an industrial plant includes creating a workflow for thechange. The method also includes assessing an impact of the change onthe control system and on at least one additional control system basedon an assessment checklist retrieved from a first database. The methodfurther includes implementing the change in the control system based onan implementation checklist retrieved from the first database. Themethod also includes testing the change implemented in the controlsystem based on a test checklist retrieved from the first database. Inaddition, the method includes documenting the workflow in a seconddatabase after completion of at least one of the assessment checklist,the implementation checklist, and the test checklist.

In a third embodiment, a method for correcting a defect in an controlsystem of an industrial plant includes creating a work order to fix thedefect, where the work order is associated with a workflow defined byinformation in a first database. The method also includes determining asolution for the defect based on information in a second database. Themethod further includes assessing an impact of the solution on thecontrol system and on at least one additional control system based on anassessment checklist retrieved from the first database. The method alsoincludes implementing the solution in the control system based on animplementation checklist retrieved from the first database. The methodfurther includes testing the solution implemented in the control systembased on a test checklist retrieved from the first database. Inaddition, the method includes documenting the work order in a seconddatabase after completion of at least one of the assessment checklist,implementation checklist, or the test checklist.

Other technical features may be readily apparent to one skilled in theart from the following figures, descriptions, and claims.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of this disclosure, reference is nowmade to the following description, taken in conjunction with theaccompanying drawings, in which:

FIGS. 1 and 2 illustrate an example workflow-based change management anddocumentation system according to this disclosure;

FIG. 3 illustrates an example client device for use in a workflow-basedchange management and documentation system according to this disclosure;

FIG. 4 illustrates an example workflow method for implementing a changeaccording to this disclosure; and

FIG. 5 illustrates an example workflow method for fixing an engineeringdefect according to this disclosure.

DETAILED DESCRIPTION

FIGS. 1 through 5, discussed below, and the various embodiments used todescribe the principles of the present invention in this patent documentare by way of illustration and should not be construed in any way tolimit the scope of the invention. Those skilled in the art willunderstand that the principles of the disclosure may be implemented inany type of suitably arranged device or system.

Industrial plants often use various control systems to perform a widevariety of operations. Configurations of the control systems are oftendocumented individually by different vendors. In addition, changes tothe configurations of the control systems (which may involve routinemaintenance, updating the systems, fixing defects in the systems, orreplacing the systems) may also be individually documented. Becausethere is no centralized system or method to perform and document changesto control systems, assessing the impacts of the changes and determiningroot causes of problems are often difficult. This can make it much moredifficult to manage and control the control systems, which in turn canmake it much more difficult to manage and control the operations of theindustrial plants.

This disclosure provides a system and method for standardizing changesto control systems in an industrial plant and documenting the changes byintegrating workflow management with documentation storage. Integrationof the workflow management functions and documentation storage functionsin a centralized system provides easier management of the controlsystems, permits users to easily assess the impacts of changes in onecontrol system to other control systems, and eases root cause analysisof any defects in any of the control systems. This can help to improvemanagement and control over the control systems, which in turn can helpto improve management and control over the operations of the industrialplants.

FIGS. 1 and 2 illustrate an example workflow-based change management anddocumentation system 100 according to this disclosure. As shown in FIG.1, the system 100 includes one or more stationary terminals or computers102, one or more mobile devices 104, and at least one workflow anddocumentation (WD) server 106. The computers 102 and mobile devices 104denote user equipment that may communicate with the WD server 106 in anysuitable manner. For example, the computers 102 or mobile devices 104could communicate with other components wirelessly, such as viacellular, WIFI, BLUETOOTH, or other wireless communication protocols.The computers 102 or mobile devices 104 could also communicate withother components in a wired manner, such as when the computers 102communicate via one or more ETHERNET networks or the mobile devices 104are placed in docking stations or otherwise physically coupled to anexternal device.

As described in more detail below, the WD server 106 supports aworkflow-based change management and documentation system. The WD server106 therefore supports workflow-based change management that isintegrated with a centralized documentation system. The workflow featurepermits the enforcement of processes and practices for an organizationthrough workflow steps, states, and approvals. The workflow feature alsopermits enforcement of safety and security checklists and complianceaudits, such as those mandated by an organization.

The WD server 106 permits users (such as via the computers 102 or mobiledevices 104) to define maintenance tasks (such as remedial, preventive,and periodic tasks) in the operation of an industrial plant ascategorical workflows. The tasks may be initiated and traced throughcompletion, tested, and documented under a digital template provided bythe system. Approvals, reviews, and cross-function communications may bedone electronically and may be easily archived. Audits required forcompliance and other needs can be easily supported. All referencedocuments of various systems and interconnections between systems in anindustrial plant may be easily available with the workflow system.

The workflow feature enables bi-directional traceability from a changerecord to a workflow and from a workflow to a corresponding changerecord and permits management of defects found in a system. This enablesa standard organization process to be enforced based on a root cause ofa defect. A workflow template allows organizations to create templatesfor their maintenance processes for handling defects and change requestwork orders.

A tighter integration of the workflow system with a documentation systemenables mapping of impacted objects into workflows, which may assist indetermining impacts of changes. Tighter integration with thedocumentation system also enables mapping of changes to correspondingchange request workflows. Any change that is not mapped to a changerequest workflow may not be approved due to such changes beingdangerous, such as from a security or safety point of view.

FIG. 2 illustrates additional details of an example implementation ofthe workflow-based change management and documentation system 100,including the WD server 106. As shown in FIG. 2, a client application202 generally provides user access to the system 100. The clientapplication 202 may be stored and executed by the computers 102 shown inFIG. 1. The client application 202 allows users to access and reviewengineering documentation, changes, or defects. The client application202 also enables the study of impact assessment when making certainchanges in industrial process control and automation systems. The clientapplication 202 may further be used to track changes and associate thechanges with corresponding change request workflows. In addition, theclient application 202 may be used to interact with workflowapplications, such as to support the creation of workflow templates, theinitiation of a workflow instance for a changes request, the addition ofan impact assessment, the performance of a checklist, or the requestingof an approval.

A mobile application 204 also generally provides user access to thesystem 100, but the mobile application 204 may be stored and executed bythe mobile devices 104 shown in FIG. 1. The mobile application 204 couldsupport the same or similar functions as the client application 202while being suitable for use by mobile devices.

The WD server 106 represents at least one computing device configured totransmit, receive, and store data and to execute applications. The WDserver 106 may be implemented as a single computing device or as acollection of computing devices. In this example, the WD server 106includes or supports an application server 206, a workflow system 208, adocumentation system 210, and a notification service 212. Theapplication server 206 generally provides application processing andrules for the documentation system 210. For example, the applicationserver 206 can collect data from and transmit data to the clientapplications 202 and the mobile applications 204. The application server206 can also route data to and from the workflow system 208,documentation system 210, and notification service 212. The applicationserver 206 denotes any suitable structure for transmitting and/orreceiving data and executing an application based on the data.

The workflow system 208 includes a workflow application server 214, aworkflow engine service 216, and a workflow database 218. The workflowapplication server 214 is configured to transmit, receive, and storedata and to execute applications related to workflow management. Theworkflow application server 214 may be implemented separate from theapplication server 206 or on the same device(s) as the applicationserver 206. The workflow application server 214 is responsible forhandling application processing and rules for one or more workflows. Theworkflow application server 214 is also responsible for visualization ofworkflow steps and current states. The visualization of workflow stepsand current states can be provided to the client applications 202 ormobile applications 204, such as via a graphical user interface (GUI),and used by users to interact with workflows, perform steps involved inthe workflows, and conduct approvals. The workflow application server214 can also be responsible for providing a GUI to the clientapplications 202 or mobile applications 204 used for authoring workflowtemplates.

The workflow engine service 216 performs state management of runningworkflows, such as by performing time-based processing of workflowstates, transitions, and notifications. For example, if a workflowapproval is pending for more than a predetermined time period (such astwo days), the workflow engine service 216 may determine that aremainder notification should be provided to the appropriate party. Insome embodiments, the workflow engine service 216 represents anapplication that may be executed in the background of the WD server 106.

The workflow database 218 represents an organized collection of dataregarding workflow templates and workflow instances. For example, theworkflow database 218 could include workflow templates, each of whichmay include a list of one or more steps that need to be performed ateach stage of the workflow. The workflow database 218 may also includethe current state and step information of each workflow in progress. Theworkflow database 218 may further store information on completedworkflows, as well as the final disposition of the completed workflows.The workflow database 218 may be implemented in any suitable manner,such as within a single database or multiple databases.

The documentation system 210 includes a documentation database 220. Thedocumentation database 220 represents a centralized organized collectionof data regarding systems in an industrial manufacturing or processingplant, such as process control and automation system componentsimplemented in the plant. For example, the documentation database 220could include engineering configurations of controls & instrumentation(C&I) systems in a plant. The documentation database 220 could alsoinclude changes in engineering configurations or defects that areidentified in the engineering configurations. The documentation database220 may be implemented in any suitable manner, such as within a singledatabase or multiple databases. The workflow database 218 and thedocumentation database 220 could also be implemented using the samedatabase(s) or using different databases.

The notification service 212 is responsible for sending notifications tousers of the system 100. For example, the notification service 212 couldgenerate email messages, text messages, or push notifications for theusers. Any actions taken by the users in response to the notificationscan be provided to the application server 206. In some embodiments, thenotification service 212 represents an application that may be executedin the background of the WD server 106.

Additional details regarding specific operations involving the WD server106 are provided below. Note that these details are examples only andthat the WD server 106 could be used in a wide variety of ways in a widevariety of industrial settings.

Although FIGS. 1 and 2 illustrate one example of a workflow-based changemanagement and documentation system 100, various changes may be made toFIGS. 1 and 2. For example, various components in FIG. 2 could becombined, further subdivided, rearranged, or omitted and additionalcomponents could be added according to particular needs.

FIG. 3 illustrates an example client device 300 for use in aworkflow-based change management and documentation system according tothis disclosure. In particular, FIG. 3 illustrates an example of theterminal or computer 102 or the mobile device 104 for use in theworkflow-based change management and documentation 100 of FIG. 1.However, the client device 300 could be used in any other workflow-basedchange management and documentation system.

As shown in FIG. 3, the client device 300 includes at least oneprocessor 302 and at least one memory 304. The processors 302 generallyoperate to process data and control the overall operation of the clientdevice 300. Each processor 302 denotes any suitable processing device,such as a microprocessor, microcontroller, digital signal processor,central processing unit (CPU), application processor (AP), communicationprocessor (CP), field programmable gate array, application specificintegrated circuit, or discrete logic devices. Each memory 304 is usedto store and facilitate retrieval of instructions and data used,generated, or collected by the client device 300. Each memory 304includes any suitable volatile or non-volatile memory device.

The client device 300 also includes or supports at least one displaydevice 306. The display devices 306 can be used to present informationto a user and optionally to receive input from a user. For example, thedisplay devices 306 could include a display 316 and a touch screen 318(which could be integrated into a single touch screen display). Thedisplay 316 could present a user interface (UI) that permits a user tointeract with the client device 300 and any software or programs beingexecuted on the client device 300 or on another device (such as the WDserver 106). The touch screen 318 may capture user input when a usertaps, slides, or otherwise touches the touch screen 318.

In addition, the client device 300 includes at least one input interface308, at least one audio device 310, at least one transceiver 312, and atleast one bus 314. The input interfaces 308 support the receipt of datafrom one or more input devices in any suitable manner. For example, aninput interface 308 could receive input from a keyboard, a keypad, amouse, an electronic pen or stylus configured to interact with thedisplay devices 306, or a touch pad. The audio devices 310 may includeat least one speaker 320 for presenting audio content and at least onemicrophone 322 for capturing audio signals.

The transceivers 312 can communicate data to or from the client device300 in any suitable manner. As noted above, any suitable communicationprotocol(s) could be supported by the transceiver(s) 312, such ascellular, WIFI, BLUETOOTH, ETHERNET, or any other or additional wirelessor wired protocols. The transceivers 312 can support the transmissionand reception of any suitable data. For example, a transceiver 312 couldtransmit completed steps and approvals of a workflow to the WD server106. The transceiver 312 could also transmit data generated via voicerecognition or manual entry.

Each bus 314 denotes any suitable communication bus that interconnectsand delivers data or other signals between components 302-312. While onebus 314 is shown here, different buses 314 could couple differentcomponents in the computer 102, or components could be coupled directlytogether without the need for a shared bus.

Although FIG. 3 illustrates one example of a client device 300 for usein a workflow-based change management and documentation system, variouschanges may be made to FIG. 3. For example, various components in FIG. 3could be combined, further subdivided, rearranged, or omitted andadditional components could be added according to particular needs.Also, computers and mobile devices come in a wide variety ofconfigurations, and FIG. 3 does not limit this disclosure to anyparticular computer or mobile device.

FIG. 4 illustrates an example workflow method 400 for implementing achange according to this disclosure. For ease of explanation, the method400 of FIG. 4 is described with respect to the WD server 106 of FIG. 2operating in the system 100 of FIG. 1. However, the workflow method 400could be used by any other suitable device and in any other suitablesystem.

As shown in FIG. 4, a change workflow is created by a user at step 402.When an control system in a plant needs routine maintenance, needs to beupdated, or needs to be replaced, a change workflow is created. Thiscould include, for example, the WD server 106 receiving a request for achange from the client application 202 or the mobile application 204. Inthe following discussion, it may be assumed that the change requestoriginated from the mobile application 204 of the mobile device 104, butthe change request could just as easily originate from the clientapplication 202 of the computer 102. When the change workflow iscreated, the workflow database 218 provides a workflow template to theuser via the workflow application server 214. The workflow templaterepresents a definition for a workflow instance that allows a user todescribe the states, steps, transition conditions, checklists, and/orapprovals to be taken to complete a workflow. In some embodiments, if aworkflow template is not available, the workflow application server 214could provide a GUI to the user via the mobile application 204 to createa workflow. Once the workflow template is selected or created, it isprovided to a user for approval. Once approved, the created workflow isthen documented in the documentation database 220.

Once the workflow is created, an impact of the change is assessed atstep 404. This could include, for example, the WD server 106 assessingthe impact that the change would have on C&I systems or other systems ofthe plant based on information stored in the documentation database 220.This could be done automatically or based on input that the WD server106 receives from other users. As a particular example, the WD server106 could contact and receive input from one or more other users, suchas a maintenance engineer. This could allow the maintenance engineer toreceive an assessment checklist from the workflow database 218 thatincludes the steps to assess the impact on the C&I or other systems ofthe plant. As the maintenance engineer checks off each item on theassessment checklist, the application server 206 can document thecompleted step in the documentation database 220 and the workflowapplication server 214. Once all steps of the assessment checklist arecompleted, the application server 206 may cause the notification service212 to notify yet another user, such as a manager, that additionalapprovals are needed. Once the additional approval is received, theadditional approval is recorded in the workflow application server 214and the documentation database 220.

Once the needed approvals are obtained, the change is implemented atstep 406. This could include, for example, the WD server 106 providingone or more of the users (such as a maintenance engineer) with animplementation checklist from the workflow database 218. As themaintenance engineer checks off each item on the implementationchecklist, the application server 206 documents the completed step inthe documentation database 220 and the workflow application server 214.Once all steps of the implementation checklist are completed, theapplication server 206 may cause the notification service 212 to notifya user, such as a manager, that an approval of the implemented change isneeded. Once the approval is received, the approval is recorded in theworkflow application server 214 and the documentation database 220.

The change is then tested at step 408. This could include, for example,the WD server 106 providing one or more of the users (such as amaintenance engineer) with a test checklist from the workflow database218. As the maintenance engineer checks off each item on the testchecklist, the application server 206 documents the completed step inthe documentation database 220 and the workflow application server 214.Once all steps of the test checklist are completed (or if not all stepscan be completed), the WD server or at least one user (such as themaintenance engineer or a manager) determines if the test passed orfailed.

If the test failed, the implementation of the change is rejected, andthe change is not deployed at step 410. In this case, the applicationserver 206 could cause the notification service 212 to request approvalfor not deploying the change. If the test passed, the change isdeployed, such as into one or more C&I or other systems of an industrialprocess control and automation system, at step 412. This could include,for example, the WD server 106 providing at least one of the users (suchas a maintenance engineer) with a deployment checklist from the workflowdatabase 218. As the maintenance engineer checks off each item on thedeployment checklist, the application server 206 documents the completedstep in the documentation database 220 and the workflow applicationserver 214. Once all steps of the deployment checklist are completed,the application server 206 may cause the notification service 212 tonotify a user, such as a manager, that an approval is needed. Once theapproval is received, the completed workflow is recorded in the workflowdatabase 218 and the documentation database 220.

FIG. 5 illustrates an example workflow method 500 for fixing anengineering defect according to this disclosure. For ease ofexplanation, the method 500 of FIG. 5 is described with respect to theWD server 106 of FIG. 2 operating in the system 100 of FIG. 1. However,the workflow method 500 could be used by any other suitable device andin any other suitable system.

As shown in FIG. 5, a work order is created by a user at step 502. Whena defect is identified in a control system in a plant, a work order iscreated to correct the defect. This could include, for example, the WDserver 106 receiving a request to create a work order from the clientapplication 202 or the mobile application 204 due to a defect associatedwith an industrial plant. In the following discussion, it may be assumedthat the request originated from the mobile application 204 of themobile device 104, but the request could just as easily originate fromthe client application 202 of the computer 102. When the work order iscreated, the workflow database 218 can provide a workflow template tothe user via the workflow application server 214. As described above inFIG. 4, the workflow template may be retrieved from the workflowdatabase 218 or created by a user. Once the workflow template isselected or created, it can be provided to a user for approval. Onceapproved, the created work order is then documented in the documentationdatabase 220.

Once the work order is created, a solution for the defect is determinedat step 504. This could include, for example, the WD server 106 or auser determining the solution by determining a root cause of the defectbased on information in the documentation database 220. Such informationin the documentation database 220 may include past configurations of C&Ior other systems, changes to the C&I or other systems that have beenimplemented, tested, or deployed, or current configurations of the C&Ior other systems.

Once a solution is determined, the impact of the solution is assessed atstep 506. This could include, for example, the WD server 106 or a user,such as a maintenance engineer, assessing the impact that the solutionwould have on the C&I or other systems of the plant based on informationstored in the documentation database 220. As a particular example, themaintenance engineer may receive a checklist from the workflow database218 that includes the steps to assess the impact on the C&I or othersystems of the plant. As the maintenance engineer checks off each itemon the assessment checklist, the application server 206 documents thecompleted step in the documentation database 220 and the workflowapplication server 214. Once all steps of the assessment checklist arecompleted, the application server 206 may cause the notification service212 to notify a user, such as a manager, that an approval is needed.Once the approval is received, the approval is recorded in the workflowapplication server 214 and the documentation database 220.

The solution is implemented at step 508. This could include, forexample, the WD server 106 providing a user, such as a maintenanceengineer, with an implementation checklist from the workflow database218. As the maintenance engineer checks off each item on theimplementation checklist, the application server 206 documents thecompleted step in the documentation database 220 and the workflowapplication server 214. Once all steps of the implementation checklistare completed, the application server 206 may cause the notificationservice 212 to notify a user, such as a manager, that an approval isneeded. Once the approval is received, the approval is recorded in theworkflow application server 214 and the documentation database 220.

The solution is tested at step 510. This could include, for example, theWD server 106 providing one or more of the users (such as a maintenanceengineer) with a test checklist from the workflow database 218. As themaintenance engineer checks off each item on the test checklist, theapplication server 206 documents the completed step in the documentationdatabase 220 and the workflow application server 214. Once all steps ofthe test checklist are completed (or if not all steps can be completed),the WD server or at least one user (such as the maintenance engineer ora manager) determines if the test passed or failed.

If the test failed, the implemented solution is rejected, and thesolution is not deployed at step 512. The application server 206 maycause the notification service 212 to request approval for not deployingthe change. If the test passed, the implemented solution is deployed,such as into one or more C&I or other systems of an industrial processcontrol and automation system, at step 514. This could include, forexample, the WD server 106 providing at least one of the users (such asa maintenance engineer) with a deployment checklist from the workflowdatabase 218. As the maintenance engineer checks off each item on thedeployment checklist, the application server 206 documents the completedstep in the documentation database 220 and the workflow applicationserver 214. Once all steps of the deployment checklist are completed,the application server 206 may cause the notification service 212 tonotify a user, such as a manager, that an approval is needed. Once theapproval is received, the completed workflow is recorded in the workflowdatabase 218 and the documentation database 220.

Although FIGS. 4 and 5 illustrate examples of workflow methods 400 and500, various changes may be made to FIGS. 4 and 5. For example, whileshown as a series of steps, various steps in each figure could overlap,occur in parallel, occur in a different order, or occur any number oftimes.

In some embodiments, various functions described in this patent documentare implemented or supported by a computer program that is formed fromcomputer readable program code and that is embodied in a computerreadable medium. The phrase “computer readable program code” includesany type of computer code, including source code, object code, andexecutable code. The phrase “computer readable medium” includes any typeof medium capable of being accessed by a computer, such as read onlymemory (ROM), random access memory (RAM), a hard disk drive, a compactdisc (CD), a digital video disc (DVD), or any other type of memory. A“non-transitory” computer readable medium excludes wired, wireless,optical, or other communication links that transport transitoryelectrical or other signals. A non-transitory computer readable mediumincludes media where data can be permanently stored and media where datacan be stored and later overwritten, such as a rewritable optical discor an erasable memory device.

It may be advantageous to set forth definitions of certain words andphrases used throughout this patent document. The terms “application”and “program” refer to one or more computer programs, softwarecomponents, sets of instructions, procedures, functions, objects,classes, instances, related data, or a portion thereof adapted forimplementation in a suitable computer code (including source code,object code, or executable code). The term “communicate,” as well asderivatives thereof, encompasses both direct and indirect communication.The terms “include” and “comprise,” as well as derivatives thereof, meaninclusion without limitation. The term “or” is inclusive, meaningand/or. The phrase “associated with,” as well as derivatives thereof,may mean to include, be included within, interconnect with, contain, becontained within, connect to or with, couple to or with, be communicablewith, cooperate with, interleave, juxtapose, be proximate to, be boundto or with, have, have a property of, have a relationship to or with, orthe like. The phrase “at least one of,” when used with a list of items,means that different combinations of one or more of the listed items maybe used, and only one item in the list may be needed. For example, “atleast one of: A, B, and C” includes any of the following combinations:A, B, C, A and B, A and C, B and C, and A and B and C.

The description in the present application should not be read asimplying that any particular element, step, or function is an essentialor critical element that must be included in the claim scope. The scopeof patented subject matter is defined only by the allowed claims.Moreover, none of the claims invokes 35 U.S.C. § 112(f) with respect toany of the appended claims or claim elements unless the exact words“means for” or “step for” are explicitly used in the particular claim,followed by a participle phrase identifying a function. Use of termssuch as (but not limited to) “mechanism,” “module,” “device,” “unit,”“component,” “element,” “member,” “apparatus,” “machine,” “system,”“processor,” or “controller” within a claim is understood and intendedto refer to structures known to those skilled in the relevant art, asfurther modified or enhanced by the features of the claims themselves,and is not intended to invoke 35 U.S.C. § 112(f).

While this disclosure has described certain embodiments and generallyassociated methods, alterations and permutations of these embodimentsand methods will be apparent to those skilled in the art. Accordingly,the above description of example embodiments does not define orconstrain this disclosure. Other changes, substitutions, and alterationsare also possible without departing from the spirit and scope of thisdisclosure, as defined by the following claims.

What is claimed is:
 1. A system comprising: a first database configuredto store one or more workflow templates associated with one or moreworkflows, each of the one or more workflows used to implement at leastone change in at least one control system of an industrial plant; asecond database configured to store one or more documents for each ofthe one or more workflows, wherein the documents include engineeringconfigurations of controls & instrumentation (C&I) systems along withchanges in engineering configurations that are identified in theengineering configurations in the at least one control system; and atleast one processor configured to communicate with at least one userequipment and to provide at least one user interface to the at least oneuser equipment, the at least one user interface configured to providethe one or more workflow templates and to receive definitions of the oneor more workflows, the at least one user interface also configured toprovide the one or more workflows for implementation of the at least onechange in the at least one control system; and wherein in response toreceiving a change request in the at least one control system change toat least one control system of the industrial plant from a user via theat least one user interface, the at least one processor is configuredto: when a workflow template from the one or more workflow templates forthe control system change requested by the change request is availablein the first database, provide the workflow template for the controlsystem change to the user via the at least one user interface; when theworkflow template from the one or more workflow templates for thecontrol system change requested by the change request is not availablein the first database, provide a graphical user interface to the uservia the at least one user interface for creating a workflow template forthe control system change requested by the change request; receiveapproval of the provided workflow template for the control systemchange; and automatically assess an impact of change in workflow for thecontrol system change requested by the change request on the controlsystem that the control system change was requested and at least oneother control system of the industrial plant.
 2. The system of claim 1,further comprising: a workflow engine service configured to performstate management of the one or more workflows.
 3. The system of claim 1,wherein the first database is further configured to store informationidentifying completed workflows.
 4. The system of claim 1, furthercomprising: a notification service configured to notify one or moreusers, via the at least one user equipment, of one or more states of theone or more workflows.
 5. The system of claim 1, wherein the first andsecond databases reside within a single database structure.
 6. Thesystem of claim 1, wherein: the one or more workflows comprise multipleworkflows; and the multiple workflows include (i) workflows formaintaining, updating, and replacing multiple control systems of theindustrial plant and (ii) workflows for correcting defects inconfigurations of the control systems.
 7. The system of claim 6, whereinthe multiple workflows further include: checklists used to assessimpacts of different changes to the control systems on other controlsystems; checklists used to implement the changes to the controlsystems; and checklists used for testing the changes to the controlsystems.
 8. A method for implementing a change in a control system of anindustrial plant, the method comprising: presenting a graphical userinterface for creating a workflow for the change; receiving a createdworkflow and documenting the created workflow in a documentationdatabase; in response to receiving and document the created workflow,providing an assessment checklist retrieved from a workflow database,the assessment checklist including one or more steps to complete and isconfigured to assist a user in assessing an impact of the change on thecontrol system and on at least one additional control system; as thesteps of the assessment checklist are completed, a processor documentingthe completed steps of the assessment checklist in the documentationdatabase; in response to completing all of the steps of the assessmentchecklist, the processor requesting approval of the created workflow; inresponse to receiving approval of the created workflow, providing animplementation checklist retrieved from a first database, theimplementation checklist includes one or more steps to complete and isconfigured to assist the user in implementing the change in the controlsystem; as the steps of the implementation checklist are completed, theprocessor documenting the completed steps of the implementationchecklist in the documentation database; providing a test checklistretrieved from the first database, the test checklist includes one ormore steps to complete and is configured to assist the user in testingthe change implemented in the control system; as the steps of the testchecklist are completed, the processor documenting the completed stepsof the test checklist in the documentation database; and documenting theworkflow in the documentation database by storing one or more documentsafter completion of at least one of the assessment checklist, theimplementation checklist, and the test checklist, wherein the documentsinclude engineering configurations of controls & instrumentation (C&I)systems along with changes in the engineering configurations that areidentified in the engineering configurations in the at least one controlsystem.
 9. The method of claim 8, wherein creating the workflowcomprises retrieving a workflow template from the first database. 10.The method of claim 8, wherein creating the workflow comprises creatinga workflow template using at least one user equipment.
 11. The method ofclaim 8, further comprising: for each step of the checklists requiringapproval, transmitting one or more notifications to one or more usersrequesting the approval.
 12. The method of claim 8, further comprising:deploying the change to the control system in response to successfultesting of the change.
 13. The method of claim 8, wherein the changealters operation of the control system and thereby alters operation ofthe industrial plant.
 14. A method for correcting a defect in a controlsystem of an industrial plant, the method comprising: presenting agraphical user interface for creating a work order to fix the defect,the work order associated with a workflow defined by information in afirst database; retrieving information in a second database to assist auser in determining a solution; receiving the solution and a processordocumenting the solution in the second database; in response toreceiving and documenting the solution in the second database, providingan assessment checklist retrieved from the first database, theassessment checklist configured to assist a user in assessing an impactof the solution on the control system and on at least one additionalcontrol system; in response to completing the assessment checklist, theprocessor requesting approval for the solution; in response to receivingapproval of the solution, providing an implementation checklistretrieved from the first database, the implementation checklist isconfigured to assist a user in implementing the solution in the controlsystem; providing a test checklist retrieved from the first database,the test checklist is configured to assist a user in testing thesolution implemented in the control system; and documenting the workorder in the second database by storing one or more documents aftercompletion of at least one of the assessment checklist, theimplementation checklist, and the test checklist, wherein the documentsinclude engineering configurations of controls & instrumentation (C&I)systems along with changes in the engineering configurations that areidentified in the engineering configurations in the at least one controlsystem; and wherein: each of the assessment checklist, implementationchecklist, and the test checklist includes multiple steps; and themethod further comprises: receiving an indication that each of themultiple steps has been completed; and documenting each completed stepin the second database as the step is completed.
 15. The method of claim14, wherein creating the work order comprises retrieving a workflowtemplate from the first database.
 16. The method of claim 14, whereincreating the work order comprises creating a workflow template using atleast one user equipment.
 17. The method of claim 14, furthercomprising: deploying the solution to the control system in response tosuccessful testing of the change.
 18. The method of claim 14, whereinthe solution alters operation of the control system and thereby altersoperation of the industrial plant.